Hi all |
Re: Hardware sizing for DOORS with terminal Server at our company, we only install the doors client onto the windows terminal server and that means it needs to meet the doors v.x.x minimum system requirements as any client. The doors database server resides on a separate server which meets the respective system requirements for the doors v x.x we are running. In addition you should consider how many users you expect at any one time to need to connect to the terminal server and have the server configured to support that requirement. I suppose that one could install the database service onto the windows terminal server, but seems to introduce some exposure to other risks and or a need to address the impact of doing so. I guess what i am trying to say is the windows terminal server is "typically" a gateway into a particular network domain, and from there, you can point to databases etc. Note: prior to doors 9.3 most documentation for this was part of downloads of client and install, now info such as this is posted online as here: http://publib.boulder.ibm.com/infocenter/doorshlp/v9/index.jsp i hope this helps... :) gsdguy |
Re: Hardware sizing for DOORS with terminal Server SystemAdmin - Fri Jan 21 13:32:12 EST 2011 sorry i missed seeing the Luca in my first response... i wanted to add that we commonly use virtual machines for our doors databases over the last few years back to 2007 i believe. we are still using pc's at user desktops to run the client as this provides the best mix for using doors with several 3rd party tools like msoffice, msvisio, and other software for in and out processing of requirements documentation and doors databases. Once you get into trying to run all the 3rd party tools on a terminal server it does not lend itself to making life easier or cheaper, at least when it comes to doors. a couple of side notes,...you will still also need to purchase and maintain the proper amount of doors licenses to run via a terminal server. There are several ideas about on how to calculate the number you might need. also, some software tools require you to purchase a # of licenses equal to number of employees can see and connect to a terminal server, that can get VERY expensive. while it would be great for small number of machines to update when versions need update, it can become more expensive prohibitive due to this reason. gsdguy |